Skip to content

chore(ci): revamp parallel test outputs clarity and conciseness - #18002

Draft
chalmerlowe wants to merge 4 commits into
mainfrom
feat/parallel-output-revamp-v2
Draft

chore(ci): revamp parallel test outputs clarity and conciseness#18002
chalmerlowe wants to merge 4 commits into
mainfrom
feat/parallel-output-revamp-v2

Conversation

@chalmerlowe

@chalmerlowe chalmerlowe commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Problem

The current output from the package checking phase (where we determine if a package should be tested OR not) in parallel system tests is noisy and difficult to read. It prints internal debug commands and multiple lines of text for every package, making it hard to quickly scan and see which packages are being tested or skipped.

Solution

This Pull Request revamps the output format of the package checking phase to be highly readable and aligned.

  • Internal debug commands have been silenced.
  • The output now uses a "State-First" format, where the decision (TEST or SKIP) and the reason are displayed first, followed by the package name and commit hash.
  • The output is aligned in columns using printf, making vertical scanning easy for humans and parsing easy for tools.

Notes to Reviewers

  • This change is purely cosmetic and does not alter the logic of package selection or test execution.
  • A harmless trigger comment was added to packages/google-cloud-testutils/setup.py to force this package to be tested in CI, allowing you to see the new output format in action. This will be removed before merging.

Example Output

TEST [changed]     google-cloud-testutils c3bdf0971c1884aac6a4690834030583e87254e1
SKIP [no_changes]  google-cloud-tasks     c3bdf0971c1884aac6a4690834030583e87254e1
SKIP [no_changes]  google-cloud-storage   c3bdf0971c1884aac6a4690834030583e87254e1

Pre-planning For Adhoc Testing:

While ad hoc testing is not yet merged to main and is not processed as a part of this PR, the expectation is that a future PR will refine this format when adhoc is added> At that time we will be able to determine why a TEST state was chosen (changed, adhoc, or both if a package has changes AND is inadvertantly included in the ad hoc list).

TEST [changed]        google-cloud-testutils c3bdf0971c1884aac6a4690834030583e87254e1
TEST [adhoc]          google-cloud-tasks     c3bdf0971c1884aac6a4690834030583e87254e1
TEST [changed,adhoc]  google-cloud-tasks     c3bdf0971c1884aac6a4690834030583e87254e1
SKIP [no_changes]     google-cloud-storage   c3bdf0971c1884aac6a4690834030583e87254e1

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request refactors the package change detection and logging logic in .kokoro/system.sh. It introduces a states array to track whether a package has changed or is part of a continuous build, and formats these states into a comma-separated string for clearer logging output. I have no feedback to provide as there are no review comments.

@chalmerlowe chalmerlowe changed the title feat(ci): revamp parallel test outputs for searchability and clarity chore(ci): revamp parallel test outputs clarity and conciseness Aug 5, 2026
@chalmerlowe chalmerlowe self-assigned this Aug 5, 2026
@chalmerlowe chalmerlowe added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Aug 5, 2026
@chalmerlowe

Copy link
Copy Markdown
Contributor Author

Added do-not-merge as a reminder to self to remove the temporary trigger.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge Indicates a pull request not ready for merge, due to either quality or timing.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant